|
|
|
|
|
|
|
In Week 2, you learned about self-testing objects, breaking up applications into subsystems, and refining use cases. This week's lessons also discuss the subsystems for the graphical user interface, workgroup and security, and internal application management. |
|
|
|
|
|
|
|
|
In the first lesson of the week, you learned how to build objects that test themselves by having methods that test their own preconditions, including making sure that the data or class type of an incoming parameter is of the type expected. Also presented in this lesson was advice on how to debug your classes as well as version control tips for classes and subsystems of classes using Visual SourceSafe. |
|
|
|
|
|
|
|
|
On Day 9, Breaking Up an Application into Subsystems, you delved deeply into the process of breaking up a proposed application into subsystems, including components. You learned how to identify and use design patterns for subsystems and their interactions and how to define, name, and apply the design pattern. Finally, you learned the particulars of describing the solution provided by the design pattern, about listing the consequences of using the design pattern, and how to use and reuse design patterns for subsystems, including analyzing and designing subsystem interfaces. |
|
|
|
|
|
|
|
|
In the next lesson, you learned the art of refining use cases as application and subsystem architecture blueprints. You learned about revisiting use cases in your environment, the problem statement, and the use-case model. This lesson also showed you how to refine user requirements into a better use-case model, as well as the art of working with end users, business analysts, executives, and project managers. You also |
|
|
|
|
|